Progress with the Westhill version
Hello Racers.
Four weeks since our announcement about the Westhill update that is coming soon, I thought it would be good to give you a short progress report.
Things are going well but, as expected, taking longer than expected.
On my side, as some of you know from other threads, I made a quick 3D mode for red-cyan anaglyph glasses, the kind that can be bought very cheaply, e.g. 4 pairs for £1. Interestingly, it needed a simple pixel shader to make it work so finally I learned to program pixel shaders, which you can do in the HLSL shader language in DirectX 9 (which LFS uses since 0.6F).
Pixel shaders open up a world of graphical possibilities, so it's a good thing to be able to do, and one thing I had to do, for the Westhill patch, was improve the "optimiser" which pre-computes which objects are visible from your position on the track path (except in open configurations, which is why the frame rate is lower on them). This used to be done in a rudimentary software render, but by using pixel shaders I can use the DX9 render which makes the optimiser work better.
With my new found excitement about these shaders, I knew the render of the cars could be done more efficiently. In the current public version, each shiny surface of the car is rendered in 3 passes, using 3 vertex shaders. One for the direct light (affected by the lightmap) one for the ambient light and another for the environment map that makes the cars shiny. I have now made a single vertex shader and pixel shader that render every polygon only once instead of 3 times and this saves a lot of frame rate. I expect to release this in an intermediate test patch next week, along with the anaglyph view mode, and some other updates, listed at the bottom of this post.
On Eric's side, he has been completing the areas between the parts of the track and the access roads. The scenery is at a new level of detail compared with our other tracks. This is partly for the fun of driving in those places in the open configs, and also for a more realistic look and feel of the place as you drive around on the track where you are supposed to be!
It's looking very nice. Eric still has some holes to fill and I still have a list of updates, for editor functions that will help Eric and a few minor things that can go in this incompatible patch. The physics will still be compatible so we don't have to delete all the hotlaps (except Westhill) but the multiplayer will be incompatible.
So, still a few weeks before the Westhill version goes into public testing, but it's all going well. Thanks for your patience and we look forward to releasing it!
Changes from 0.6F to Test Patch 0.6F2
(intermediate, compatible update before Westhill version)
[EDIT : (as already stated above...) I expect to release this next week]
Two new 3D formats in TV / monitor /projector mode :
- red-cyan anaglyph
cheap red-cyan glasses are required
more expensive glasses can correct red (left) eye focus
colour perception is reduced and different in each eye
do not use this mode for a long time
- cross-eyed view
no equipment needed
the 3D world appears small
right eye looks at left image / left eye looks at right image
this is difficult for some people (with normal vision)
stop immediately if you feel any discomfort
do not use this mode for a long time
Skin downloading when watching a replay :
If a car or helmet skin in a replay is not available at LFS World
when you start the replay (with low or high res skins selected)
but you already have the skin in the other resolution then that
skin in the other resolution will be used instead of a plain car
Fixes :
Crash when using a wheel button assigned to /rift toggle command
Crash when pressing e.g. F8 when /press F8 was assigned to F8 key
Graphics :
New car shaders giving higher frame rate when many cars on screen
FIX : Car lighting momentarily vertical as car entered a shadow
Four weeks since our announcement about the Westhill update that is coming soon, I thought it would be good to give you a short progress report.
Things are going well but, as expected, taking longer than expected.
On my side, as some of you know from other threads, I made a quick 3D mode for red-cyan anaglyph glasses, the kind that can be bought very cheaply, e.g. 4 pairs for £1. Interestingly, it needed a simple pixel shader to make it work so finally I learned to program pixel shaders, which you can do in the HLSL shader language in DirectX 9 (which LFS uses since 0.6F).
Pixel shaders open up a world of graphical possibilities, so it's a good thing to be able to do, and one thing I had to do, for the Westhill patch, was improve the "optimiser" which pre-computes which objects are visible from your position on the track path (except in open configurations, which is why the frame rate is lower on them). This used to be done in a rudimentary software render, but by using pixel shaders I can use the DX9 render which makes the optimiser work better.
With my new found excitement about these shaders, I knew the render of the cars could be done more efficiently. In the current public version, each shiny surface of the car is rendered in 3 passes, using 3 vertex shaders. One for the direct light (affected by the lightmap) one for the ambient light and another for the environment map that makes the cars shiny. I have now made a single vertex shader and pixel shader that render every polygon only once instead of 3 times and this saves a lot of frame rate. I expect to release this in an intermediate test patch next week, along with the anaglyph view mode, and some other updates, listed at the bottom of this post.
On Eric's side, he has been completing the areas between the parts of the track and the access roads. The scenery is at a new level of detail compared with our other tracks. This is partly for the fun of driving in those places in the open configs, and also for a more realistic look and feel of the place as you drive around on the track where you are supposed to be!
It's looking very nice. Eric still has some holes to fill and I still have a list of updates, for editor functions that will help Eric and a few minor things that can go in this incompatible patch. The physics will still be compatible so we don't have to delete all the hotlaps (except Westhill) but the multiplayer will be incompatible.
So, still a few weeks before the Westhill version goes into public testing, but it's all going well. Thanks for your patience and we look forward to releasing it!
Changes from 0.6F to Test Patch 0.6F2
(intermediate, compatible update before Westhill version)
[EDIT : (as already stated above...) I expect to release this next week]
Two new 3D formats in TV / monitor /projector mode :
- red-cyan anaglyph
cheap red-cyan glasses are required
more expensive glasses can correct red (left) eye focus
colour perception is reduced and different in each eye
do not use this mode for a long time
- cross-eyed view
no equipment needed
the 3D world appears small
right eye looks at left image / left eye looks at right image
this is difficult for some people (with normal vision)
stop immediately if you feel any discomfort
do not use this mode for a long time
Skin downloading when watching a replay :
If a car or helmet skin in a replay is not available at LFS World
when you start the replay (with low or high res skins selected)
but you already have the skin in the other resolution then that
skin in the other resolution will be used instead of a plain car
Fixes :
Crash when using a wheel button assigned to /rift toggle command
Crash when pressing e.g. F8 when /press F8 was assigned to F8 key
Graphics :
New car shaders giving higher frame rate when many cars on screen
FIX : Car lighting momentarily vertical as car entered a shadow
Last edited by Scawen, .
Why do you need to know what Eric thinks about multithreading? I don't see it as some controversial thing which would polarize opinions...
It's pretty obvious what Eric would think. He would be happy any time I can give the graphics or physics systems more power. He would approve if I spent some time on it, but obviously not when some other things are more important, like supporting him with this Westhill update, as I am doing at the moment (reason for the delay on the anaglyph 3D).
It's pretty obvious what Eric would think. He would be happy any time I can give the graphics or physics systems more power. He would approve if I spent some time on it, but obviously not when some other things are more important, like supporting him with this Westhill update, as I am doing at the moment (reason for the delay on the anaglyph 3D).
New Version 0.6F and Progress Report
Dear LFS Racers,
Today we release an new update of Live for Speed with 3D support and announce another version that is coming soon with a much improved Westhill track.
Version 0.6F:
Available today and well tested by forum visitors, this new update supports 3D devices including TVs, projectors, headsets and the Oculus Rift. While developing it, we also moved onto DirectX 9 which allows for better graphical effects in future while still allowing LFS to run on older versions of Windows and on Linux (using the Wine compatibility software). This version remains fully compatible with 0.6E with many improvements and fixes.
Read more about the patch and how to get it on the 0.6F information page.
Westhill Update:
Available soon... as the development for S3 has been taking some time, we thought it would be good to update something for our existing license holders. The best thing to update was the Westhill track which was always sparse and underdeveloped. The International configuration has been improved in many places, particularly in the twisty sequence of bends in the far corner which is now more challenging. There is a new National configuration, bearing off from the International track after the first right and left bends, involving some interesting gradient changes and technical bends. The scenery has been developed to a higher level of detail and you can drive around the access roads in the open configurations.
You can see images of the new track on our screenshots page.
The configurations are complete and good to drive. At this point Eric is still finishing some buildings and filling some holes in the scenery. Scawen is making some improvements and optimisations to deal with the higher level of detail. We expect to release this version for testing in a few weeks, but remember that sometimes interesting things can come up that make things take a little longer than planned.
Further Progress:
After the Westhill update, Eric will continue with the S3 tracks he has been working on. Scawen will continue with the new tyre model. The new tyres currently feel good to drive but some work needs to be done on heat, pressure, friction, tyre load sensitivity and wear which are all closely linked.
- LFS Developers
Today we release an new update of Live for Speed with 3D support and announce another version that is coming soon with a much improved Westhill track.
Version 0.6F:
Available today and well tested by forum visitors, this new update supports 3D devices including TVs, projectors, headsets and the Oculus Rift. While developing it, we also moved onto DirectX 9 which allows for better graphical effects in future while still allowing LFS to run on older versions of Windows and on Linux (using the Wine compatibility software). This version remains fully compatible with 0.6E with many improvements and fixes.
Read more about the patch and how to get it on the 0.6F information page.
Westhill Update:
Available soon... as the development for S3 has been taking some time, we thought it would be good to update something for our existing license holders. The best thing to update was the Westhill track which was always sparse and underdeveloped. The International configuration has been improved in many places, particularly in the twisty sequence of bends in the far corner which is now more challenging. There is a new National configuration, bearing off from the International track after the first right and left bends, involving some interesting gradient changes and technical bends. The scenery has been developed to a higher level of detail and you can drive around the access roads in the open configurations.
You can see images of the new track on our screenshots page.
The configurations are complete and good to drive. At this point Eric is still finishing some buildings and filling some holes in the scenery. Scawen is making some improvements and optimisations to deal with the higher level of detail. We expect to release this version for testing in a few weeks, but remember that sometimes interesting things can come up that make things take a little longer than planned.
Further Progress:
After the Westhill update, Eric will continue with the S3 tracks he has been working on. Scawen will continue with the new tyre model. The new tyres currently feel good to drive but some work needs to be done on heat, pressure, friction, tyre load sensitivity and wear which are all closely linked.
- LFS Developers
By the way, do you start to see why Eric doesn't like posting here? These crazy conversations you end up having with people who can write but can't read. They are quite mentally tiring because you have to say the same thing dozens of times and still it is ignored and the conversation goes round and round like a wheel of deja vu. It seems like people have nothing to do so they play a fun game "wind up the developer who likes talking to the community". "All we have to do is keep repeating Microsoft marketing at him, regardless of his reply, and soon he'll become agitated which is great fun". That's probably not the case but it starts to look that way, when people talk to you and don't read the reply.
After a while it seems like there isn't any point saying anything because what you say is ignored.
OK, I know what will happen now. Someone will tell me that DX9 is only used by dinosaurs, XP is the Model T Ford of operating systems, it's time to move on to the latest and greatest thing.
But I've already explained why it isn't possible or desirable or necessary to do so.
https://www.lfsforum.net/showt ... php?p=1857760#post1857760
After a while it seems like there isn't any point saying anything because what you say is ignored.
OK, I know what will happen now. Someone will tell me that DX9 is only used by dinosaurs, XP is the Model T Ford of operating systems, it's time to move on to the latest and greatest thing.
But I've already explained why it isn't possible or desirable or necessary to do so.
https://www.lfsforum.net/showt ... php?p=1857760#post1857760
Thanks guys, I know a lot of people really do understand and accept our way of doing things.
I think you misunderstood what I said a little bit, because I didn't say that I don't care about the community. Just that I can't worry about the dip in progress. After a decade of really hard work (12 to 15 hour days used to be the normal thing for me) it would have been great if we could just reel off another decade just the same. But, with the benefit of hindsight, neither Eric nor I were capable of continuing like that.
I am trying to make the point that the unplanned dip, which came about for whatever reason, could be beneficial in the long run if we can work in a sustainable way. For example, we are still alive which is a good start and I'm also a real life racer now who considers his tyres and races on tracks that vary a lot due to the weather!
I think you misunderstood what I said a little bit, because I didn't say that I don't care about the community. Just that I can't worry about the dip in progress. After a decade of really hard work (12 to 15 hour days used to be the normal thing for me) it would have been great if we could just reel off another decade just the same. But, with the benefit of hindsight, neither Eric nor I were capable of continuing like that.
I am trying to make the point that the unplanned dip, which came about for whatever reason, could be beneficial in the long run if we can work in a sustainable way. For example, we are still alive which is a good start and I'm also a real life racer now who considers his tyres and races on tracks that vary a lot due to the weather!
Hello everyone!
The developers are all alive and working on LFS.
Eric has been working on new tracks. He slowed up a bit during some of the great English summer which we don't get very often. I have enjoyed test driving on two of his new tracks which look great and I look forward to the time when they can be released.
I am still working on the tyre physics, though I haven't really made serious progress this year. I also enjoyed the summer, did a lot of cycling and running too. It's a better hobby than smoking like I used to, and I really enjoy it. But the good news is it won't pay the bills!
LFS income has gradually gone down as it always does between updates. That that has increased the urgency of finishing the tyre physics. So I plan to get down to it, make the appropriate approximations and sort out a good physically based system, with enough assumptions to make it workable, accepting that total realism is an unachievable goal.
I just got a bit excited about stereoscopic 3d support, which some people will like because they'll be able to see LFS in 3d on a 3d TV, if their TV supports "side-by-side" or "top and bottom" mode. Also headsets should be supported if they accept one of those output modes. The old headsets that require specific support and sequential output will not be supported. For example a Sony HMZ works but a Vuzix VR920 does not. A more recent Vuzix should work but the field of view is not really good enough to give you peripheral vision. I'm not sure how much it will benefit the Oculus Rift at the moment. I think that depends on a pixel shader to provide the proper distortion, which I think is not available in D3D8. Anyway, one of the output options will be non-squashed (full) side-by-side 3D, which may possibly make it easier to use the Oculus Rift. Anyway it is a step in that direction. It does appear that the current Oculus Rift's resolution is too low for a racing simulator at the moment. Anyway I should be able to post a 3d test patch in a few days, I'm guessing early next week. Some people will enjoy that, though I realise most people, like me, don't have 3d equipment.
Victor is still with us, although he has indeed got another job, which looks like a really good one, putting his excellent skills to more use. I'm pleased for him about that, as his job here wasn't often really full time, although he is an absolutely vital member of our team. He needed a job as well because our profit share isn't one third each and depends on our actual contributions to the project. Victor started later and never has so much work, so for that reason only, his profit share was a bit of a tight squeeze to live on, specially with the gradual reduction in profits while we are waiting for a serious update.
People ask why I don't come here more often with progress reports. But there hasn't been enough progress to give a report. And it's not appealing to come here and say that. Every month I've thought I would be making more progress, and would have some good progress to report the following month. Hope you see what I mean...
Anyway, we do have to pay the bills and I'm very interested to get the better feeling tyre model out there for everyone to enjoy. You've heard it all before so I don't expect great enthusiasm. It will take a while yet, but hopefully not too long.
The developers are all alive and working on LFS.
Eric has been working on new tracks. He slowed up a bit during some of the great English summer which we don't get very often. I have enjoyed test driving on two of his new tracks which look great and I look forward to the time when they can be released.
I am still working on the tyre physics, though I haven't really made serious progress this year. I also enjoyed the summer, did a lot of cycling and running too. It's a better hobby than smoking like I used to, and I really enjoy it. But the good news is it won't pay the bills!
LFS income has gradually gone down as it always does between updates. That that has increased the urgency of finishing the tyre physics. So I plan to get down to it, make the appropriate approximations and sort out a good physically based system, with enough assumptions to make it workable, accepting that total realism is an unachievable goal.
I just got a bit excited about stereoscopic 3d support, which some people will like because they'll be able to see LFS in 3d on a 3d TV, if their TV supports "side-by-side" or "top and bottom" mode. Also headsets should be supported if they accept one of those output modes. The old headsets that require specific support and sequential output will not be supported. For example a Sony HMZ works but a Vuzix VR920 does not. A more recent Vuzix should work but the field of view is not really good enough to give you peripheral vision. I'm not sure how much it will benefit the Oculus Rift at the moment. I think that depends on a pixel shader to provide the proper distortion, which I think is not available in D3D8. Anyway, one of the output options will be non-squashed (full) side-by-side 3D, which may possibly make it easier to use the Oculus Rift. Anyway it is a step in that direction. It does appear that the current Oculus Rift's resolution is too low for a racing simulator at the moment. Anyway I should be able to post a 3d test patch in a few days, I'm guessing early next week. Some people will enjoy that, though I realise most people, like me, don't have 3d equipment.
Victor is still with us, although he has indeed got another job, which looks like a really good one, putting his excellent skills to more use. I'm pleased for him about that, as his job here wasn't often really full time, although he is an absolutely vital member of our team. He needed a job as well because our profit share isn't one third each and depends on our actual contributions to the project. Victor started later and never has so much work, so for that reason only, his profit share was a bit of a tight squeeze to live on, specially with the gradual reduction in profits while we are waiting for a serious update.
People ask why I don't come here more often with progress reports. But there hasn't been enough progress to give a report. And it's not appealing to come here and say that. Every month I've thought I would be making more progress, and would have some good progress to report the following month. Hope you see what I mean...
Anyway, we do have to pay the bills and I'm very interested to get the better feeling tyre model out there for everyone to enjoy. You've heard it all before so I don't expect great enthusiasm. It will take a while yet, but hopefully not too long.
This is a typically outrageous and ridiculous interpretation of something I said which has an obvious meaning.
It's absolutely obvious what "unsubscribe" means, to click the "unsubscribe" option so that I don't receive email notifications of new posts on this thread. That would be, of course, to save me wasting so many minutes of the one life that I have, reading posts like yours and edge3147's.
If I was saying that I have decided to throw away my career on a whim, that suddenly developing a program that I care greatly about means nothing to me any more because a couple of people on the internet made a couple of irritating posts, then I'd say something about it, wouldn't I? You really have a bizarre view of the world. YOU are the kind of person that makes Eric avoid posting here.
You complain about our communication. Why not learn to read?
[ After posting this, I'll unsubscribe again - no that doesn't mean I'm giving up my career and going to look for a job ]
Last edited by Scawen, .
Reason : fixed typo
Well, I haven't seen what Lynce did with Fern Bay, though I am sure it is very good.
But I am not going to get drawn into off topic conversations that have nothing to do with the problem of the day or the points in my previous post.
You are just causing spam that obscures what I said a few posts above.
So what will happen? Someone else will come and ask me the same thing.
You see? This is what my post was trying to explain. Now do you see why Eric doesn't post here?
But I am not going to get drawn into off topic conversations that have nothing to do with the problem of the day or the points in my previous post.
You are just causing spam that obscures what I said a few posts above.
So what will happen? Someone else will come and ask me the same thing.
You see? This is what my post was trying to explain. Now do you see why Eric doesn't post here?
I have explained this many times in the past. I'm reluctant to say it again, because I expect that I am just opening the floodgates for a barrage of questions and various detailed explanations of why our strategy is absolutely ridiculous, why we are being dishonest and so on.
But here goes... and unfortunately this is once again, a historical text that I have said over and over again. We planned to release the Scirocco then soon after, Rockingham (the start of S3 content). But we discovered that it was impossible to make the car handle realistically or safely while using realistic settings. So I thought, let's take a few weeks and sort out this tyre model. That took me on a long journey of development. Never did I think, what a waste of time this has been, let's go back to the old flawed model and start releasing the things which we haven't released because of the flaws in the tyre model. No, we still want to sort out the tyre model before releasing anything.
This is absolutely not that Victor and I are wishing Eric would release new content and he is refusing to do so. That is one of the false imaginings from certain people in the community. We want to sort out the tyres then release the VW and then Rockingham and other things as planned.
As I've said, over and over and over again, Eric is working on new content. You just will not believe it. Eric doesn't post here because he doesn't like the way some people take any words we say, twist them round to mean something completely different then hold them against us. And because any minor slip up in our text can lead to years of seemingly personal attacks. I'm reluctant to make this reply, as I said, this normally ends up drawing me into ridiculous discussions until I just have to unsubscribe or close the thread. So I can understand his reluctance to post here. It would be nice if he did, but he doesn't want to.
Right, that is the same Anakin who did this in 0.6B. He claims to be helping LFS development, and said he achieved his aim by getting me back to work (actually taking me off the tyre physics and onto hacker protection - though I agree there was useful development of the multiplayer code). But he doesn't want to help by letting us know how he did this. If he would send us an email of explanation, that would help LFS development, because I would be able to get back to the tyre physics and some editor tools Eric has asked me for. But his current approach is not helping to advance the speed of LFS development.
Anyway, I would like to see a log produced from the host at the time he joined it, hopefully with the replay also recorded on the host.
Anyway, I would like to see a log produced from the host at the time he joined it, hopefully with the replay also recorded on the host.
On topic :
I hope to release a dedicated host test update either today or tomorrow, that should at least prevent the user being connected with a user name you cannot type, or a user name that does not match the user id.
Off topic :
Although development has been slow for some time, we are still motivated on LFS, which we do regard as a long term thing. I must admit this year both Eric and I have had some slow months and some months in which we didn't do much LFS at all.
In both our cases that has been partly for external reasons which will not have a long term negative effect, and also partly a need for a slight break after several years of hard work.
In my case I have got into some sport (cross country running and cycling) which has obvious benefits I don't need to explain, after two decades without. That occupied my mind a lot (in a good way) and has been great for me and my family, but not great in an immediate sense for LFS's development this summer. The journey of tyre physics development has been a tough one, round and round, forwards and backwards these couple of years. I feel this summer break has helped me mentally. I've got some answers and plan to get that tyre stuff sorted out so we can get back to the fun stuff and a faster development rate in the S3 period.
I hope to release a dedicated host test update either today or tomorrow, that should at least prevent the user being connected with a user name you cannot type, or a user name that does not match the user id.
Off topic :
Although development has been slow for some time, we are still motivated on LFS, which we do regard as a long term thing. I must admit this year both Eric and I have had some slow months and some months in which we didn't do much LFS at all.
In both our cases that has been partly for external reasons which will not have a long term negative effect, and also partly a need for a slight break after several years of hard work.
In my case I have got into some sport (cross country running and cycling) which has obvious benefits I don't need to explain, after two decades without. That occupied my mind a lot (in a good way) and has been great for me and my family, but not great in an immediate sense for LFS's development this summer. The journey of tyre physics development has been a tough one, round and round, forwards and backwards these couple of years. I feel this summer break has helped me mentally. I've got some answers and plan to get that tyre stuff sorted out so we can get back to the fun stuff and a faster development rate in the S3 period.
Progress Report December 2011
A short progress report posted on www.lfs.net :
Dear LFS Racers,
We hope you had a good year in 2011. In June we released 0.6B, the best version of LFS so far. Since then we have been continuing to work towards the new tyre model and the S3 upgrade which we plan to release after the physics update.
Scawen has been further developing the virtual tyre test rig, a detailed model of a tyre's structure, to work out various values for the in-game tyre model. For example, what is the contact patch length, width and pressure for a given vertical deflection and how does the tyre's shape change with forces, torques and camber. These depend on the dimensions and structure of a tyre. By making the in-game tyres behave in a similar way, the driving experience will be as realistic as possible.
In the left part of the image, the yellow lines show the radial cords of the carcass. The orange and green lines show the steel belts and the cap ply. The right side of the image illustrates the carcass thickness which gives some rigidity even without air pressure.
Eric has been working on the S3 content. After the physics update and the VW Scirocco are released as a free update for all S1 and S2 license holders, we will work towards the S3 update which will provide more tracks and cars to S3 license holders. As usual for an upgrade, the cost of your existing license will be deducted from the full price.
We wish you a happy 2012, and we'll release the updates as soon as we can!
- LFS Developers
Dear LFS Racers,
We hope you had a good year in 2011. In June we released 0.6B, the best version of LFS so far. Since then we have been continuing to work towards the new tyre model and the S3 upgrade which we plan to release after the physics update.
Scawen has been further developing the virtual tyre test rig, a detailed model of a tyre's structure, to work out various values for the in-game tyre model. For example, what is the contact patch length, width and pressure for a given vertical deflection and how does the tyre's shape change with forces, torques and camber. These depend on the dimensions and structure of a tyre. By making the in-game tyres behave in a similar way, the driving experience will be as realistic as possible.
In the left part of the image, the yellow lines show the radial cords of the carcass. The orange and green lines show the steel belts and the cap ply. The right side of the image illustrates the carcass thickness which gives some rigidity even without air pressure.
Eric has been working on the S3 content. After the physics update and the VW Scirocco are released as a free update for all S1 and S2 license holders, we will work towards the S3 update which will provide more tracks and cars to S3 license holders. As usual for an upgrade, the cost of your existing license will be deducted from the full price.
We wish you a happy 2012, and we'll release the updates as soon as we can!
- LFS Developers
That sign is not linked into LFS speed limits. I just added it so that hosters, through InSim programs, could implement a 50 km/h speed limit if they wanted to. I just copied Eric's 80 km/h sign from Blackwood and changed the texture on the front.
Well the chalk arrows have not changed, forward always meant forward (same direction as a start position).
So your point really is that you would prefer markers to be the opposite way. But they came from Aston and that's just the way they were made. They face "forward". So the "front" of them has the writing on it. That's how Eric first made them in the modeller and I really think that is the normal way that anyone would build an object. What you would call the front of a car and what you would call the front of a sign...
Only problem is you like the front of signs to oppose the front of a car. So the signs that you see on a road are all pointing backwards.
Anyway, that's just how it is so it will not be changed.
So your point really is that you would prefer markers to be the opposite way. But they came from Aston and that's just the way they were made. They face "forward". So the "front" of them has the writing on it. That's how Eric first made them in the modeller and I really think that is the normal way that anyone would build an object. What you would call the front of a car and what you would call the front of a sign...
Only problem is you like the front of signs to oppose the front of a car. So the signs that you see on a road are all pointing backwards.
Anyway, that's just how it is so it will not be changed.
Maybe you do, but I don't.
Remember, LFS came before InSim. LFS paths are created as a looped path with an arbitrary start and end point. This path contains lighting info, echo info, visible objects info and so on. These are generated in one direction only and they are flipped for the reverse path. Eric might change the position of the finish line and there is no need to regenerate the path. There is absolutely no need for the finish line to be at node zero, and I can't write the code to assume that in a general case, so there has never been a need to rearrange the paths to align with the finish line, and move all the data around between nodes when the path is flipped. The work involved for that would be quite tremendous and have bug potential, when all you need to do is subtract the finish line from your car's path node, if you want to find its position relative to the finish line.
relative_node = (lfs_reported_node + num_nodes - finish_line_node) % num_nodes;
I can write that in 10 seconds but it would be days of work to try and rearrange the way it is represented internally in LFS.
Heh, this is like talking to my 5 year old son, who asks so many questions! And here it's not good, because each person who asks a question takes yet another 5 to 10 minutes of my time, so reducing the updates I can put in today's patch. It would be better to accept what I say, because I have thought it through.
This an INTERMEDIATE patch with the same old tyre physics. That means, the old hotlaps are staying valid. It's not a good time to delete all the old hotlaps, when the tyre physics is still the same. So, we are not releasing track updates that would make all the hotlaps go out of sync.
That is quite apart from the fact that Eric is working on S3 content at the moment. I think it is ok for me to say, that he doesn't like being asked to switch from one thing to another. Some people like to switch tasks all the time - I have no choice - but Eric does not like that, he likes to stay focussed on what is is doing. This is sort of "my" patch and I don't think he really wants to be involved. Not that I have asked him - I've already explained above, we don't want to put the hotlaps out of sync. I've gone into a lot of detail how one thing led to another on the road to this patch.
So, please, try to understand, I'm working very hard to try and get a patch out today and I don't want to explain every single decision on every step of the way.
Yes, the fix is automatic, so it should fix any cases. But if you have found more false collisions (hitting something that isn't there) other than the Fern Bay pit walls beside the gantries, then I's like to having a look to make sure it's covered by the same fix.
The SHIFT+U views are stored in the .tvw files in the data\views folder.
I don't know what you mean about the autocross lights, they seem to work ok. Maybe you are talking about the sequence of the lights? I can't change that easily, Eric did it how he wanted it, and it is stored in the lights object.
progress
Last Thursday I thought I'd have a "quick look" at that. And tried the updated segment collisons system that I did for the ray check in the new SHIFT+U mode. Segments are the curvy things that form the track, fences, walls, pit garages, some buildings, etc. Most things that you do hit are segments, unless they are "objects". I keep calling this a collision detection system but it's not just collisions, it is actually the whole contact detection system that the tyres also use to detect the ground.
Well, it was promising but problems soon showed up (like crazy collisions on things that aren't there due to incorrect assumptions). That took me on one of these development journeys, trying so many different ways to sort out the problems. There I will cut a long story short.
Finally this Wednesday I got to a usable version of a new 3d based segment collision system that is more reliable and better than any LFS has had before and you can scrape a Blackwood pit garage wall when you drive out, without being flung anywhere. Only problem was that it used about 50% more cpu.
On Thursday I was trying and trying to speed it up and finally came to a nice optimisation that means the new, accurate collision system uses less cpu than the old one. Eric, Victor and I have tested it and can't find any problems and we hope you'll find it's a lot better than the old system.
Old hotlaps can still run although they would have gone OOS because the old collision detection system is in there and that is used when you run a pre-Z30 replay.
Tuesday 12
==========
Objects in escape road at BL chicane removed from open configs
List of Hosts now shows X or Y if an open config is selected
Car reset now works on open configs (if reset is enabled)
Wear limit for changing tyres can be set to 100% (never)
Compatibility : new packets not sent if connected to old host
Compatibility : new host does not allow old versions to connect
Wednesday 13
============
FIX : Clutch axis / button was not reported from Controls screen
Surface friction of objects is now CONCRETE (was previously ICE)
Discovered that many KY2 and KY3 replays were OOS due to objects
Implemented SPR version check so old replays can still be watched
Added a new Ramp2 which is the same as Ramp1 but 2.8 metres wide
Ramp1 and Ramp2 are stored in the exe and loaded into all tracks
Thursday 14
===========
Improved Y character to make it look less like V character
FIX : Host restart exploit found by Luigi Auriemma (23 Aug 2009)
FIX : High altitude layout objects appeared under ground on load
Updated contact detection to fix pit garage exit collisions
Friday 15 to Tuesday 18
=======================
New segment collision detection system
Weds 20
=======
Finished a usable version of the new segment collision system
Objects closing pit road at SO removed from open configs
Various stacks of tyres at SO removed from open configs
Thurs 21
========
Optimised the segment collisions - now faster than old version
Implemented VOB mod protection (physical changes will cause OOS)
FIX : clicking on a car in SHIFT+U sometimes put view inside car
InSim : added more info to the IS_CON packet
Friday 22
=========
Updated follow car option in SHIFT+U mode
Added a minimum height slider bar in "more" options
New command /ck cancels any kick or ban votes in progress
New command /cv cancels any votes (kick, ban, restart, etc)
You can drive there as part of a larger configuration but you can't put a start grid on it, as you can only use existing grids (or the single autocross start position).
No, that new section is not opened up in this patch. It's very unfinished there, experimental and lacks barriers so you can just fall into the underworld. I don't know how far Eric will go with it in the future.
New test patch coming soon (not VWS or S3)
Dear LFS Racers,
Since the release of Z28 there have been various fixes and improvements that were not related to the new physics. Some of them were already added into my Z28 compatible version as well as the new version. But until now there weren't enough significant updates to release a new version, while Z28 was so stable.
NOTE : This patch is mainly compatible with Z28, so does NOT have the new tyre physics, the VW Scirocco or any S3 content. It is an intermediate update with some interesting improvements for LFS while I continue with the tyre physics. The new version can connect to Z28 hosts, but Z28 cannot connect to the new version's hosts.
The main things in this patch :
- New free view in SHIFT+U mode - not bounded by the path
- Improved collisions with unmovable objects (e.g. red barriers)
- Number of autocross objects increased to 800 (was 512)
- Open track configurations allowing you to drive anywhere
- Collision detection and reporting system (via InSim)
- Graphical optimisations improving frame rates
- Many other fixes and improvements
The story behind the new patch :
A few weeks ago I was working on some track editor improvements that Eric had requested, when I came across a fix that could possibly affect key presses in multi byte languages. An LFS user in Japan kindly tested the change, to make sure the fix didn't break the text input. I added a few updates from the new version into the patch before sending it to him.
Talking to Victor about possibly releasing the updates in a patch, he asked if it was possible to do a quick fix in SHIFT+U mode to help with his LFS Record program. I have long been a little frustrated in SHIFT+U mode so I got a bit carried away with that and rewrote all the camera control. It took a few weeks (that made me nervous as I really want to finish the new physics) but the result is a lot nicer to use. You can move the camera around freely, not bounded to the track path. The editor is fully aware of where your mouse is pointing and that helps with mouse movement and object positioning.
Because the new view is not locked to the path of the track, LFS does not know which objects are visible, so the whole track must be drawn. I managed to find several optimisations that improved the frame rate in this situation, and that gave me a thought : if you can be in SHIFT+U mode and draw everything, then how about allowing "open configurations" where you can drive around anywhere in a track area, with the barriers removed? I thought that would make the patch more interesting, and managed to get it done in a few days.
To make the open configurations useful, you need to put barriers up using the autocross system. But the unmovable barriers were famously troublesome, often throwing your car several metres in the air if you touched a red and white barrier. Looking into this, I found that I was able to improve these collisions a lot without any major changes. It doesn't seem to affect the hotlap replays (tested on all the world records).
Over last weekend I added a collision detection system, that can send information about collisions to InSim. And today I've increased the maximum length of message packets, which will be helpful for InSim programmers.
If all goes well, it should be possible to release this as a test patch within one to two weeks. There are a few things left on my list, including VOB mod protection and some small InSim updates. I am aiming for one week - I do want to get back to the physics - but I know that finishing things off sometimes takes longer than expected.
Here is the full list of updates :
SHIFT+U mode :
New free view mode replaces the old "low" and "high" path modes
Object or ground targeted by the mouse pointer is now detected
Left mouse button moves view point by "dragging" target point
Double click to move view point directly towards target point
Mouse wheel moves view point towards or away from target point
Left + Right mouse buttons rotate view point around the target
Arrow key movement follows ground below view point when possible
Store up to 10 views per track configuration with SHIFT+NUMBER
Recall a stored view with CTRL+NUMBER (or click on the button)
Click on a car to follow it / move away to stop following
Autocross editor :
Maximum number of autocross objects is now 800 on all tracks
Object positioning is much better - using mouse target detection
Less CPU / better checks when adding / moving / deleting objects
FIX : Could click on invisible replay slider when buttons visible
FIX : Could add marshall circles out of bounds then undeletable
FIX : N key in SHIFT+U with options on caused overlapping text
Open configurations :
New "drive anywhere" open configs (CTRL in track select screen)
Open configs can be selected with text command like /track=SO1X
Open configs can be used as racing circuits by adding checkpoints
Checkpoints can now be up to 62 metres wide to include pit lane
Optimisations :
Removed continual small memory leaks (materials list corruption)
Number plate generation is much faster - reducing pit-out glitch
Frame rate increased - drawing most world objects is much faster
Interface :
Unlock screen now renames unnamed player to user name on exit
Clicking selected track loads that track (like pressing ENTER)
Windows messages processed in a cleaner way (affects key presses)
Mouse movements are processed more efficiently (drag / slide)
FIX : Mouse look info could go off screen in some languages
FIX : An invalid view could be selected when no cars in race
FIX : Meeting room scroll bar was invisible in recent versions
FIX : Text commands could be used to load layout in hotlap mode
Graphics / Audio :
Improved display of help text / lesson text / welcome messages
F9 tyre diagram and SHIFT+L suspension diagrams now antialiased
Improved tyre optimisation - no missing parts of deflected tyres
Entry screen logo and frame are now drawn if a dialog box is open
FIX : In Driver Options the driver intersected with world objects
FIX : Reset from behind a barrier at South City could stop sound
FIX : Missing shadow on ground near fences at Autocross track
Multiplayer :
List of hosts can now show hosts you are not licensed to join
Host name is displayed in task bar and window title (if Latin)
Host options are now readable when opened from game setup screen
Default host IP address is now 127.0.0.1 (address of local host)
CTRL+SHIFT now displays time and date in all multiplayer replays
Removed TCP filter that allowed old versions in the list of hosts
FIX : Some problems resulting from multiple requests to join race
FIX : Pit stop did not end if car was knocked out of the pit lane
FIX : Some crashes that could result from an invalid unlock state
FIX : Some missing images (e.g. track select) caused LFS to crash
FIX : Suspension could incorrectly stay broken on remote computer
InSim :
NLP / MCI minimum time interval reduced to 40 ms (was 50 ms)
New collision packet gives details of contact between two cars
Longer IS_MST now up to 128 chars / specify sound / send to all
Misc :
Misc options : F9 / F10 accelerometer can be shown as one value
Improved detection of invalid window positions when starting LFS
URL command is now case insensitive - LFS:// or lfs:// both work
Security : InSim can no longer be initialised from a URL command
Cruise : no need to drive a lap before serving DT / SG penalty
Cruise : current lap is not displayed if lap timing is disabled
FIX : Improved collisions with unmovable objects (red barriers)
FIX : InSim camera with vertical pitch would cause LFS to crash
FIX : OutGaugePack ID was always zero regardless of ID in cfg.txt
Since the release of Z28 there have been various fixes and improvements that were not related to the new physics. Some of them were already added into my Z28 compatible version as well as the new version. But until now there weren't enough significant updates to release a new version, while Z28 was so stable.
NOTE : This patch is mainly compatible with Z28, so does NOT have the new tyre physics, the VW Scirocco or any S3 content. It is an intermediate update with some interesting improvements for LFS while I continue with the tyre physics. The new version can connect to Z28 hosts, but Z28 cannot connect to the new version's hosts.
The main things in this patch :
- New free view in SHIFT+U mode - not bounded by the path
- Improved collisions with unmovable objects (e.g. red barriers)
- Number of autocross objects increased to 800 (was 512)
- Open track configurations allowing you to drive anywhere
- Collision detection and reporting system (via InSim)
- Graphical optimisations improving frame rates
- Many other fixes and improvements
The story behind the new patch :
A few weeks ago I was working on some track editor improvements that Eric had requested, when I came across a fix that could possibly affect key presses in multi byte languages. An LFS user in Japan kindly tested the change, to make sure the fix didn't break the text input. I added a few updates from the new version into the patch before sending it to him.
Talking to Victor about possibly releasing the updates in a patch, he asked if it was possible to do a quick fix in SHIFT+U mode to help with his LFS Record program. I have long been a little frustrated in SHIFT+U mode so I got a bit carried away with that and rewrote all the camera control. It took a few weeks (that made me nervous as I really want to finish the new physics) but the result is a lot nicer to use. You can move the camera around freely, not bounded to the track path. The editor is fully aware of where your mouse is pointing and that helps with mouse movement and object positioning.
Because the new view is not locked to the path of the track, LFS does not know which objects are visible, so the whole track must be drawn. I managed to find several optimisations that improved the frame rate in this situation, and that gave me a thought : if you can be in SHIFT+U mode and draw everything, then how about allowing "open configurations" where you can drive around anywhere in a track area, with the barriers removed? I thought that would make the patch more interesting, and managed to get it done in a few days.
To make the open configurations useful, you need to put barriers up using the autocross system. But the unmovable barriers were famously troublesome, often throwing your car several metres in the air if you touched a red and white barrier. Looking into this, I found that I was able to improve these collisions a lot without any major changes. It doesn't seem to affect the hotlap replays (tested on all the world records).
Over last weekend I added a collision detection system, that can send information about collisions to InSim. And today I've increased the maximum length of message packets, which will be helpful for InSim programmers.
If all goes well, it should be possible to release this as a test patch within one to two weeks. There are a few things left on my list, including VOB mod protection and some small InSim updates. I am aiming for one week - I do want to get back to the physics - but I know that finishing things off sometimes takes longer than expected.
Here is the full list of updates :
SHIFT+U mode :
New free view mode replaces the old "low" and "high" path modes
Object or ground targeted by the mouse pointer is now detected
Left mouse button moves view point by "dragging" target point
Double click to move view point directly towards target point
Mouse wheel moves view point towards or away from target point
Left + Right mouse buttons rotate view point around the target
Arrow key movement follows ground below view point when possible
Store up to 10 views per track configuration with SHIFT+NUMBER
Recall a stored view with CTRL+NUMBER (or click on the button)
Click on a car to follow it / move away to stop following
Autocross editor :
Maximum number of autocross objects is now 800 on all tracks
Object positioning is much better - using mouse target detection
Less CPU / better checks when adding / moving / deleting objects
FIX : Could click on invisible replay slider when buttons visible
FIX : Could add marshall circles out of bounds then undeletable
FIX : N key in SHIFT+U with options on caused overlapping text
Open configurations :
New "drive anywhere" open configs (CTRL in track select screen)
Open configs can be selected with text command like /track=SO1X
Open configs can be used as racing circuits by adding checkpoints
Checkpoints can now be up to 62 metres wide to include pit lane
Optimisations :
Removed continual small memory leaks (materials list corruption)
Number plate generation is much faster - reducing pit-out glitch
Frame rate increased - drawing most world objects is much faster
Interface :
Unlock screen now renames unnamed player to user name on exit
Clicking selected track loads that track (like pressing ENTER)
Windows messages processed in a cleaner way (affects key presses)
Mouse movements are processed more efficiently (drag / slide)
FIX : Mouse look info could go off screen in some languages
FIX : An invalid view could be selected when no cars in race
FIX : Meeting room scroll bar was invisible in recent versions
FIX : Text commands could be used to load layout in hotlap mode
Graphics / Audio :
Improved display of help text / lesson text / welcome messages
F9 tyre diagram and SHIFT+L suspension diagrams now antialiased
Improved tyre optimisation - no missing parts of deflected tyres
Entry screen logo and frame are now drawn if a dialog box is open
FIX : In Driver Options the driver intersected with world objects
FIX : Reset from behind a barrier at South City could stop sound
FIX : Missing shadow on ground near fences at Autocross track
Multiplayer :
List of hosts can now show hosts you are not licensed to join
Host name is displayed in task bar and window title (if Latin)
Host options are now readable when opened from game setup screen
Default host IP address is now 127.0.0.1 (address of local host)
CTRL+SHIFT now displays time and date in all multiplayer replays
Removed TCP filter that allowed old versions in the list of hosts
FIX : Some problems resulting from multiple requests to join race
FIX : Pit stop did not end if car was knocked out of the pit lane
FIX : Some crashes that could result from an invalid unlock state
FIX : Some missing images (e.g. track select) caused LFS to crash
FIX : Suspension could incorrectly stay broken on remote computer
InSim :
NLP / MCI minimum time interval reduced to 40 ms (was 50 ms)
New collision packet gives details of contact between two cars
Longer IS_MST now up to 128 chars / specify sound / send to all
Misc :
Misc options : F9 / F10 accelerometer can be shown as one value
Improved detection of invalid window positions when starting LFS
URL command is now case insensitive - LFS:// or lfs:// both work
Security : InSim can no longer be initialised from a URL command
Cruise : no need to drive a lap before serving DT / SG penalty
Cruise : current lap is not displayed if lap timing is disabled
FIX : Improved collisions with unmovable objects (red barriers)
FIX : InSim camera with vertical pitch would cause LFS to crash
FIX : OutGaugePack ID was always zero regardless of ID in cfg.txt
OK, thanks for the comments.
I think that nearly all possible points have been made now (from the community's side).
I'm sure it would have been different if we had known in advance how long this development stage would take, I guess we could have tried to plan other releases in the meantime. But it has always seemed like I was near to finishing the tyre physics, so no change of plan was required.
Remember it was the Scirocco that showed up the issues in the tyre physics (there were already known tyre physics issues but we couldn't get the Scirocco to drive as safely as a real one does while restricting ourselves to a realistic setup). So, releasing the Scirocco has been out of the question until the tyre physics system is quite close to reality.
Releasing Rockingham has also been out of the question. We want to release a real track when the behaviour of the cars is right (not perfect, just close enough so the bumps feel right and the lap times are just like real ones).
Who knows, if I had known in advance that the tyre model would take so long, maybe Eric would have thought that he should focus on some S1 / S2 content updates. With the benefit of hindsight, it's easy to pick holes in what we have done and point out the mistakes we have made. But as I said, we always thought that in a few weeks or a couple of months, the new tyres would be ready to roll.
But the carcass simulation, which I had to look into because the tread simulation model clearly ignored too much of how a tyre actually behaves, took me in a whole new direction for a good part of last year. A long time of studying and finding out a lot more about tyres than I knew before, and had never thought I'd need to know. It made my head spin quite often, I'm not an eighteen year old on a university course. I couldn't even read this stuff for full eight hour days, had to take it a bit easy at times.
But still I usually thought I was near the end. So that is probably the reason for our dreadful "strategy" and lack of communication. It wasn't a strategy at all, and I didn't want to communicate until I got solid results.
I am fully aware that this post isn't going to convince many people. But I thought I'd write it anyway, to help you see slightly more from my point of view.
I will unsubscribe from this thread now, which I followed up to this point. But it's a bit too distracting to receive the email notifications and too tempting to come in here and read the latest posts, which takes me away from research and development.
I think that nearly all possible points have been made now (from the community's side).
I'm sure it would have been different if we had known in advance how long this development stage would take, I guess we could have tried to plan other releases in the meantime. But it has always seemed like I was near to finishing the tyre physics, so no change of plan was required.
Remember it was the Scirocco that showed up the issues in the tyre physics (there were already known tyre physics issues but we couldn't get the Scirocco to drive as safely as a real one does while restricting ourselves to a realistic setup). So, releasing the Scirocco has been out of the question until the tyre physics system is quite close to reality.
Releasing Rockingham has also been out of the question. We want to release a real track when the behaviour of the cars is right (not perfect, just close enough so the bumps feel right and the lap times are just like real ones).
Who knows, if I had known in advance that the tyre model would take so long, maybe Eric would have thought that he should focus on some S1 / S2 content updates. With the benefit of hindsight, it's easy to pick holes in what we have done and point out the mistakes we have made. But as I said, we always thought that in a few weeks or a couple of months, the new tyres would be ready to roll.
But the carcass simulation, which I had to look into because the tread simulation model clearly ignored too much of how a tyre actually behaves, took me in a whole new direction for a good part of last year. A long time of studying and finding out a lot more about tyres than I knew before, and had never thought I'd need to know. It made my head spin quite often, I'm not an eighteen year old on a university course. I couldn't even read this stuff for full eight hour days, had to take it a bit easy at times.
But still I usually thought I was near the end. So that is probably the reason for our dreadful "strategy" and lack of communication. It wasn't a strategy at all, and I didn't want to communicate until I got solid results.
I am fully aware that this post isn't going to convince many people. But I thought I'd write it anyway, to help you see slightly more from my point of view.
I will unsubscribe from this thread now, which I followed up to this point. But it's a bit too distracting to receive the email notifications and too tempting to come in here and read the latest posts, which takes me away from research and development.
Progress Report December 2010
News from www.lfs.net :
Dear LFS Racers,
We hope you have had a good year.
The stable Z28 has been the latest version for a long time now, while we have been working on things for the long term future of LFS. As many of you know, the tyre physics system is being updated so all the cars will behave that bit closer to reality. It has proved to be a challenging and unpredictable project, involving a lot of studying, mathematics, testing and rewriting.
Sometimes, we had a version that felt good to drive and it seemed that soon we would be able to release it to the community. But then we found situations where the simulation produced incorrect results, leading to further investigations into the way tyres perform in various circumstances and why they do so. One thing tends to lead to another and for a while it seems that the more you learn about tyres, the more you realise that there is so much more to find out!
Scawen has written a little more about tyre design and simulation in case you would like to get a bit more technical.
The VW Scirocco and Rockingham have seemed quite close to release for some time now, but we decided to wait for the updated tyres because these things from the real world will be best experienced with the most realistic physics system. Eric has been working on some more S3 content but he would like to get nearer to finishing before we show any new pictures.
Victor has recently produced a special program "LFS Record" which can help you to produce smooth movies from Live for Speed, using advanced camera control. It is still in a beta stage at the moment. The program has a lot of features - too much to describe here, so if you do make movies or would like to have a go, take a look at the LFS Record thread on our forum.
- LFS Developers
Dear LFS Racers,
We hope you have had a good year.
The stable Z28 has been the latest version for a long time now, while we have been working on things for the long term future of LFS. As many of you know, the tyre physics system is being updated so all the cars will behave that bit closer to reality. It has proved to be a challenging and unpredictable project, involving a lot of studying, mathematics, testing and rewriting.
Sometimes, we had a version that felt good to drive and it seemed that soon we would be able to release it to the community. But then we found situations where the simulation produced incorrect results, leading to further investigations into the way tyres perform in various circumstances and why they do so. One thing tends to lead to another and for a while it seems that the more you learn about tyres, the more you realise that there is so much more to find out!
Scawen has written a little more about tyre design and simulation in case you would like to get a bit more technical.
The VW Scirocco and Rockingham have seemed quite close to release for some time now, but we decided to wait for the updated tyres because these things from the real world will be best experienced with the most realistic physics system. Eric has been working on some more S3 content but he would like to get nearer to finishing before we show any new pictures.
Victor has recently produced a special program "LFS Record" which can help you to produce smooth movies from Live for Speed, using advanced camera control. It is still in a beta stage at the moment. The program has a lot of features - too much to describe here, so if you do make movies or would like to have a go, take a look at the LFS Record thread on our forum.
- LFS Developers
I don't know, you'd have to ask Eric.
As I said before, this thread is Tyre Physics Progress Report + Scirocco discussion.
If you are starting to think this is random question time for Scawen, please think again... maybe it's time to close the thread.
I said something because I had something to say, not because I was forced to. I am quite immune to the moaning that goes on, it doesn't disturb me much at all - it's just what happens on forums. And there are many people here with a perfect understanding of what we are doing, and they do explain it to others round here sometimes.
For a long time there was nothing to say, with some half developed tyre physics and unfinished AI drivers. When I had something to say, I said it. Hope you understand, as many others do!
It's up to Eric what of his work gets released, never have I tried to stop something of his being released!
I've just scanned through the last few pages of the thread. I haven't looked at the thread for a long time, as I've been working a lot recently.
I think you are not correct about the contempt. We're just improving this simulator. I'm trying to program the tyres to behave as realistic as possible. It takes a lot of investigation and testing.
The reason I don't make progress reports is not contempt. It just doesn't make any sense to me to do, say, monthly progress reports. One of them says "I'm working on the tyre physics" and then the next month "I'm still working on the tyre physics" and so on. I just want to say something when there is something interesting to say. But the tyre physics has been a lot of development, a lot of testing and trying new things, finding it did some things well and others not so well. Changing some things, looking for reference material to refine constants, taking a break, coming up with a new idea to test, trying it out, taking some wrong turns, investigating something that turned out impossible, rewriting something, finding a better result, and so on...
Maybe you would suggest that all those twists and turns along the journey of development is exactly what I should be writing in the weekly or monthly progress reports, but actually I don't want to. When I am following a line of investigation, I don't want to say what I am looking at, instead I just want to get on with it and see if it turns out right or wrong in the end. It's kind of a private activity, not sure how to explain that.
I don't want to give any quantifiable evidence of progress at the moment. I suppose that would be a video or some graphs of tyre forces? No, I just want to get on with it. For example today I woke up with an idea to try which might have a subtle effect on the force outputs from tyres in some situations. It's a pleasing one because it can be coded in a few minutes and will be easily visible on the generated force graphs, unlike some things that take days to write. I don't want to say what it is, it's just something I'm looking into. Sorry to everyone who would like insight into every step of the tyre physics development but it's something I do for my own interest and to come up with really nice handling cars that our community will enjoy, and that's nice because it should give us more sales eventually as well. I'm not interested in doing something like writing a book on tyre physics development, if you see what I mean.
But what I can say is...
I think the tyre physics have come along a lot recently. There were some significant changes over quite a long time this year and when I found the handling was quite interesting and certain old issues were sorted, I started to look into the tyre heating, trying to get a version ready again for the testers. That meant sorting out the AI drivers, who only knew the old physics system. If they could drive well in the new tyre physics, they could drive consistent laps and so inform me if the tyre heating was working well.
The AI ended up being about three weeks of work, and I found it personally quite an interesting development time - which is good because that's what I'm here for! Anyway their grip prediction systems are a lot better and they can now drive quite close to the limit, the best and most reliable AI drivers yet seen in LFS. At some point I'd really like to work on their overtaking code, though that is not a high priority for this physics update patch.
So the AI could be crossed off that published list of big things to be done, and I feel the tyres are getting close. I've been testing them out with Eric and Victor for the last two weeks. They have been coming up with interesting comments and leading me to further investigations and improvements. I'm trying to get the version ready for our private beta testers to have a go. Also looking at notes I have here, specific comments from our testers, the last time they did some testing. I try to deal with each point then cross it off the list. No point giving them back a version that still has issues they mentioned before.
From experience I have learned that it's not worth giving the beta testers a version that I still know is flawed. While there is still plenty for me to work on full time, and Eric and Victor are pleased with what they see but are still able to demonstrate situations where they think the handling is not quite like reality, the best thing to do is just carry on. For how long, I don't know. Not everything goes as expected. Some things I try make strangely little or surprisingly large differences and sometimes they open up a new area of investigation. Personally I am surprised overall how much there has been to learn and understand about the behaviour of tyres.
Today I thought I'd just have a look at this thread, but there are too many new pages for me to read in detail. Anyway, you may be assured we have not stopped development. I guess if we stopped development then we'd make a post about it. I'm not sure how that would happen, maybe if I got run over or contracted a fatal illness or perhaps someone will come and offer me a flight to the moon but I have to train at NASA for a couple of years. Unlikely, and there's really nothing better I can do than work on this simulator. I just don't want to write about every step on the development path, so that's why there is a long time between progress reports.
Last edited by Scawen, .
FGED GREDG RDFGDR GSFDG